docs: record verified VM import and SSH setup #52
+42
−9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alekskjo
approved these changes
Oct 15, 2026
There was a problem hiding this comment.
Looks good! The documentation now accurately records the verified VM migrations and repeatable import of 51 venues, while clearly distinguishing this from the remaining persistent backend service and frontend GraphQL integration work.
Both checks are green. Approved ✅
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The backend docs still describe VM verification as pending. This records the verified 2026-10-14 migration and import of 51 Trondheim venues into
tapfinder_dev, including a repeat import that preserved IDs and review values.It also explains how to open the local SSH tunnel, why
ssh -Nstays running quietly, and the distinction between NTNU login credentials and the database password. The setup links to the public NTNU VPN guide.Validation:
Frontend GraphQL integration and a persistent backend service on the VM remain separate work.